Your data has issues
There is a problem
- 1000 entries must have valid geometry
| Reference | Name | Tree preservation order | Uprn | Address text | Point | Geometry | Notes | Felled date | Entry date | Start date | End date |
|---|---|---|---|---|---|---|---|---|---|---|---|
| T8 - PS/540/15/390 | Wolverton Road | T8 |
Unexpected geom type |
2026-05-23 | 2015-04-20 | ||||||
| T9 - PS/540/15/390 | Wolverton Road | T9 |
Unexpected geom type |
2026-05-23 | 2015-04-20 | ||||||
| T10 - PS/540/15/390 | Wolverton Road | T10 |
Unexpected geom type |
2026-05-23 | 2015-04-20 | ||||||
| T11 - PS/540/15/390 | Wolverton Road | T11 |
Unexpected geom type |
2026-05-23 | 2015-04-20 | ||||||
| T1 - PS/540/15/335 | On Land Within The Front Garden Of 43 High Street | T1 |
Unexpected geom type |
2026-05-23 | |||||||
| T2 - PS/540/15/335 | On Land Within The Front Garden Of 43 High Street | T2 |
Unexpected geom type |
2026-05-23 | |||||||
| T3 - PS/540/15/335 | On Land Within The Front Garden Of 43 High Street | T3 |
Unexpected geom type |
2026-05-23 | |||||||
| T4 - PS/540/15/335 | On Land Within The Front Garden Of 43 High Street | T4 |
Unexpected geom type |
2026-05-23 | |||||||
| T5 - PS/540/15/335 | On Land Within The Front Garden Of 43 High Street | T5 |
Unexpected geom type |
2026-05-23 | |||||||
| T6 - PS/540/15/335 | On Land Within The Front Garden Of 43 High Street | T6 |
Unexpected geom type |
2026-05-23 | |||||||
| T1 - PS/540/15/371 | Selkirk Drive | T1 |
Unexpected geom type |
2026-05-23 | 2012-11-30 | ||||||
| T2 - PS/540/15/371 | Selkirk Drive | T2 |
Unexpected geom type |
2026-05-23 | 2012-11-30 | ||||||
| T3 - PS/540/15/371 | Selkirk Drive | T3 |
Unexpected geom type |
2026-05-23 | 2012-11-30 | ||||||
| T4 - PS/540/15/371 | Selkirk Drive | T4 |
Unexpected geom type |
2026-05-23 | 2012-11-30 | ||||||
| T12 - PS/540/15/390 | Wolverton Road | T12 |
Unexpected geom type |
2026-05-23 | 2015-04-20 | ||||||
| T13 - PS/540/15/390 | Wolverton Road | T13 |
Unexpected geom type |
2026-05-23 | 2015-04-20 | ||||||
| T14 - PS/540/15/390 | Wolverton Road | T14 |
Unexpected geom type |
2026-05-23 | 2015-04-20 | ||||||
| T15 - PS/540/15/390 | Wolverton Road | T15 |
Unexpected geom type |
2026-05-23 | 2015-04-20 | ||||||
| T16 - PS/540/15/390 | Wolverton Road | T16 |
Unexpected geom type |
2026-05-23 | 2015-04-20 | ||||||
| T17 - PS/540/15/390 | Wolverton Road | T17 |
Unexpected geom type |
2026-05-23 | 2015-04-20 | ||||||
| T18 - PS/540/15/390 | Wolverton Road | T18 |
Unexpected geom type |
2026-05-23 | 2015-04-20 | ||||||
| T19 - PS/540/15/390 | Wolverton Road | T19 |
Unexpected geom type |
2026-05-23 | 2015-04-20 | ||||||
| T20 - PS/540/15/390 | Wolverton Road | T20 |
Unexpected geom type |
2026-05-23 | 2015-04-20 | ||||||
| T21 - PS/540/15/390 | Wolverton Road | T21 |
Unexpected geom type |
2026-05-23 | 2015-04-20 | ||||||
| T22 - PS/540/15/390 | Wolverton Road | T22 |
Unexpected geom type |
2026-05-23 | 2015-04-20 | ||||||
| T23 - PS/540/15/390 | Wolverton Road | T23 |
Unexpected geom type |
2026-05-23 | 2015-04-20 | ||||||
| T24 - PS/540/15/390 | Wolverton Road | T24 |
Unexpected geom type |
2026-05-23 | 2015-04-20 | ||||||
| T25 - PS/540/15/390 | Wolverton Road | T25 |
Unexpected geom type |
2026-05-23 | 2015-04-20 | ||||||
| T26 - PS/540/15/390 | Wolverton Road | T26 |
Unexpected geom type |
2026-05-23 | 2015-04-20 | ||||||
| T27 - PS/540/15/390 | Wolverton Road | T27 |
Unexpected geom type |
2026-05-23 | 2015-04-20 | ||||||
| T28 - PS/540/15/390 | Wolverton Road | T28 |
Unexpected geom type |
2026-05-23 | 2015-04-20 | ||||||
| T29 - PS/540/15/390 | Wolverton Road | T29 |
Unexpected geom type |
2026-05-23 | 2015-04-20 | ||||||
| T30 - PS/540/15/390 | Wolverton Road | T30 |
Unexpected geom type |
2026-05-23 | 2015-04-20 | ||||||
| T31 - PS/540/15/390 | Wolverton Road | T31 |
Unexpected geom type |
2026-05-23 | 2015-04-20 | ||||||
| T32 - PS/540/15/390 | Wolverton Road | T32 |
Unexpected geom type |
2026-05-23 | 2015-04-20 | ||||||
| T33 - PS/540/15/390 | Wolverton Road | T33 |
Unexpected geom type |
2026-05-23 | 2015-04-20 | ||||||
| T34 - PS/540/15/390 | Wolverton Road | T34 |
Unexpected geom type |
2026-05-23 | 2015-04-20 | ||||||
| T35 - PS/540/15/390 | Wolverton Road | T35 |
Unexpected geom type |
2026-05-23 | 2015-04-20 | ||||||
| T36 - PS/540/15/390 | Wolverton Road | T36 |
Unexpected geom type |
2026-05-23 | 2015-04-20 | ||||||
| T37 - PS/540/15/390 | Wolverton Road | T37 |
Unexpected geom type |
2026-05-23 | 2015-04-20 | ||||||
| T38 - PS/540/15/390 | Wolverton Road | T38 |
Unexpected geom type |
2026-05-23 | 2015-04-20 | ||||||
| T39 - PS/540/15/390 | Wolverton Road | T39 |
Unexpected geom type |
2026-05-23 | 2015-04-20 | ||||||
| T40 - PS/540/15/390 | Wolverton Road | T40 |
Unexpected geom type |
2026-05-23 | 2015-04-20 | ||||||
| T41 - PS/540/15/390 | Wolverton Road | T41 |
Unexpected geom type |
2026-05-23 | 2015-04-20 | ||||||
| T42 - PS/540/15/390 | Wolverton Road | T42 |
Unexpected geom type |
2026-05-23 | 2015-04-20 | ||||||
| T43 - PS/540/15/390 | Wolverton Road | T43 |
Unexpected geom type |
2026-05-23 | 2015-04-20 | ||||||
| T44 - PS/540/15/390 | Wolverton Road | T44 |
Unexpected geom type |
2026-05-23 | 2015-04-20 | ||||||
| T45 - PS/540/15/390 | Wolverton Road | T45 |
Unexpected geom type |
2026-05-23 | 2015-04-20 | ||||||
| T1 - PS/540/15/377 | Wolverton Road | T1 |
Unexpected geom type |
2026-05-23 | 2015-01-15 | ||||||
| T2 - PS/540/15/377 | Wolverton Road | T2 |
Unexpected geom type |
2026-05-23 | 2015-01-15 |
Showing rows 201 to 250 of 1000
How to fix this issue
Your data is missing a geometry.
The Tree guidance explains how to fix the issue:
geometry
The boundary of the tree as a single polygon or multipolygon value. All points in the polygon must be in the WGS84 coordinate reference system.
If you’re providing geometry in a CSV, geometry should be in well-known text (WKT).
You must provide a point or geometry for each tree. You may provide both.
Example: MULTIPOLYGON (((1.188829 51.23478,1.188376 51.234909,1.188381 51.234917,1.187912 51.235022...
If you’re providing geometry in a GeoJSON, GML or Geopackage, use the associated geometry format.
How to improve Milton Keynes City Council’s data
- Fix the errors indicated
- Use the check service to make sure the data meets the standard
- Publish the updated data on the endpoint URL